Wireless beacon connections for providing digital letters of credit on detection of a user at a location

ABSTRACT

There are provided systems and methods for wireless beacon connections for providing digital letters of credit on detection of a user at a location. A payment provider may authorize use of one or more wireless beacons at a merchant location. When a user arrives at the merchant location, the user may be checked in through a communication device in possession of the user. Once checked in to the merchant location, the payment provider may determine and amount of credit to extend to the user based on the user&#39;s credit worthiness (for example, their credit rating, asset to debt ratio, etc.). The payment provider may then generate a letter of credit, which the payment provider may limit in use by time, location, etc. The payment provider may communicate the letter of credit to the user for use at the merchant location.

CROSS REFERENCED TO RELATED APPLICATIONS

This application is a continuation of U.S. application Ser. No.14/675,658, filed on Mar. 31, 2015, and issued as U.S. Pat. No.9,626,721 on Apr. 18, 2017, the contents of which are incorporated byreference in its entirety.

TECHNICAL FIELD

The present application generally relates to wireless beacons and morespecifically to wireless beacon connections for providing digitalletters of credit on detection of a user at a location.

BACKGROUND

A user may visit various merchant locations where the user may wish topurchase one or more items. The user may provide cash to settletransactions, or may provide payment to the merchant using anotherpayment instrument, such as a banking account, payment card (e.g.,credit, debit, and/or gift card), or through a payment account with apayment provider. However, use of cash presents significant risk to theuser, especially in large transactions where the user may not wish toplace themself in risk of robbery or theft. Moreover, use of otherpayment instruments requires the merchant to perform backend processingto insure the legitimacy of the payment instrument and whether thepayment instrument is valid for the amount of the purchase. In somecases, such as checks using a checking account, the risk of fraud orinsufficient funds is significant to the merchant. Further, somemerchants and/or payment providers may wish to provide credit options tothe user to entice the user to purchase items. However, processingcredit worthiness at the time of checkout for a transaction may beundesirable as it can be time consuming.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram of a networked system suitable forimplementing the processes described herein, according to an embodiment;

FIG. 2 is an exemplary merchant environment with users receiving limiteduse digital letters of credit on arrival at a merchant location for usein transactions with a merchant at the merchant location, according toan embodiment;

FIG. 3 is an exemplary system environment showing a user's communicationdevice receiving a limited use digital letter of credit from a paymentprovider based on the user's credit worthiness and utilizing the limiteduse digital letter of credit for a transaction with a merchant device,according to an embodiment;

FIG. 4 is a flowchart of an exemplary process for wireless beaconconnections for providing digital lets of credit on detection of a userat a location, according to an embodiment; and

FIG. 5 is a block diagram of a computer system suitable for implementingone or more components in FIG. 1, according to an embodiment.

Embodiments of the present disclosure and their advantages are bestunderstood by referring to the detailed description that follows. Itshould be appreciated that like reference numerals are used to identifylike elements illustrated in one or more of the figures, whereinshowings therein are for purposes of illustrating embodiments of thepresent disclosure and not for purposes of limiting the same.

DETAILED DESCRIPTION

Provided are methods that provide wireless beacon connections forproviding digital letters of credit on detection of a user at alocation. Systems suitable for practicing methods of the presentdisclosure are also provided.

Various merchant locations may provide short range wirelesscommunications with a device for a user (e.g., a consumer or purchaserat a merchant location), such as through beacons using one or more ofBluetooth Low Energy (BLE) communication protocol, LTE Directcommunication protocol, WiFi communication protocol, etc. These beaconsmay be set up at a location and communicate with devices to alert usersof check-in services through their device. The beacons may establish aconnection with a merchant device and/or server to communicateinformation to effectuate a check-in at the merchant location for theuser and/or complete transactions between the merchant and the user. Thebeacons may provide additional functionality, such as establishing aconnection with a payment provider server, which may offer services tothe user (e.g., payment and/or credit services). The beacons maycommunicate with the devices directly, including information stored inthe beacons. The beacons may also allow the user's device to communicatewith a device or server attached to, or in communication with, thebeacon, such as a device or server of a merchant and/or paymentprovider.

A merchant's location may offer one or more products, goods, and/orservices for sale, referred to herein as an “item” or “items.” Theitem(s) may correspond to a perishable item for sale at the merchant'slocation. A merchant's location may correspond to a retail store, ashopping market, a mall location, or other physical location where auser, such as a consumer or purchaser, may visit to purchase items. Themerchant and/or payment provider may utilize the short range wirelessbeacons at the merchant's location to communicate with a device of theuser. For example, the short range wireless beacons may be establishedthroughout the merchant location, such as at an entrance of thelocation, throughout aisles or shopping areas of the location, and/or ata checkout counter. The beacons may employ BLE, LTE Direct, WiFi, orother communications that emit a signal receivable by the user's device.The communication may include an identifier for the beacon, the user,the merchant, and/or the payment provider.

A user may set up their communication device to passively monitor forBLE, LTE Direct, WiFi, or other communication signals from the beacon.When the communication device detects the signal and verifies the one ormore identifiers, both the communication device and the beacon may rampup in power and establish a connection, where the connection may furtherenable the communication device to communicate with the merchant and/orpayment provider. The connection may be completed automatically when thecommunication device is in range of the beacon, or may be completedafter prompting the user to check-in when the communication device is inrange of the beacon. The connection established with the beacon maygenerate connection information identifying that the user has checked-into the merchant's location through the wireless beacon. The beacon mayprovide the connection information to the merchant's device or server toeffectuate a check-in for the user. The beacon may further provide theconnection information to the payment provider, which may provide one ormore payment services to the user.

Thus, the payment provider may receive connection information having anidentifier for the user. The payment provider may utilize the identifierto determine how credit worthy the user is. For example, the paymentprovider may access, retrieve, and/or determine one or more indicatorsof credit worthiness for the user. Indicators of credit worthiness mayinclude a credit rating, past transactions by the user, securityverifications on identity of the user (e.g., how likely the checked-inuser is actually the identified user and not a fraudulent usermisrepresenting their identification), known financial accounts of theuser, net worth or other value of the indicator, actual or obtainablecollateral provided by the user, or other indicator of trust infinancial value of the user. The payment provider may determine whetherthe payment provider may provide credit to the user (e.g., meeting atleast a threshold score) and/or a value of the credit worthiness (e.g.,an amount of credit to extend to the user, which may be dependent on themerchant, location, time, day, etc. In other embodiments, the credit maybe solely dependent on user credit worthiness independent of otherfactors, such that the value of credit worthiness would be the same forthe user at any given time, regardless of location, merchant, and otherfactors.

Once the payment provider has determined an amount of credit to extendto the user, the payment provider may generate a digital letter ofcredit to provide to the user and/or the merchant. The digital letter ofcredit may honor charges of up to and/or including the amount of thecredit extended to the user. The digital letter of credit may allow forthe user to complete payment for one or more transactions with themerchant using the digital letter of credit. The payment provider maythen honor payment for the transaction(s) conducted with the digitalletter of credit by providing payment to the merchant and resolving theamount with the user. For example, the digital letter of credit mayallow for the user to purchase $100 of goods at the merchant usingcredit extended to the user, where the payment provider may providepayment for up to and including $100 of goods to the merchant on behalfof the user. The digital letter of credit may be established so thatwhen received by the merchant, such as through a merchant device, theletter of credit verifies that the payment provider will honor theamount of credit extended to the user in the digital letter of credit.Thus, the merchant may asynchronously receive payment for a transactionless than or in the amount of the extended credit at a later point intime than during processing of the transaction.

The digital letter of credit may be limited by the amount of creditextended to the user. The digital letter of credit may further be oflimited use depending on factors established by the payment providerwhen generating the letter of credit. For example, a limited use letterof credit may be limited in use by one or more of time, location,merchant, and/or type of purchase. The payment provider may limit anamount of time the limited use digital letter of credit is valid (e.g.,2 hours from establishment of the digital letter of credit and/orcommunication of the digital letter of credit to the user'scommunication device/merchant device), a location for where the limiteduse digital letter of credit is valid (e.g., only the merchant locationfor which the user checked in to), a merchant with which the limited usedigital letter of credit is valid (e.g., the merchant name or chain forwhich the user checked in to), and a type of purchase with which thelimited use digital letter of credit is valid (e.g., only certain itemspurchasable in the transaction). The credit worthiness of the user mayaffect the limitations on use of the digital letter of credit. Moreover,information about the user, the user's location, and/or the merchant mayaffect the limitations on use. For example, an amount of time a customernormally spends at the merchant, if the user is detected away from themerchant, and/or types of items for sale at the merchant's location mayaffect the limitations on use.

Once the limited use digital letter of credit is determined by thepayment provider, the limited use digital letter of credit may becommunicated to the user's communication device and/or a merchant deviceat the merchant's location. The merchant device may retain the limiteduse digital letter of credit for the user so that when the user verifiestheir identity on checkout for a transaction (e.g., after bringing itemsto a checkout counter of the merchant), the merchant may process thetransaction using the limited use digital letter of credit. If thetransaction exceeds the limitations on use in the limited use digitalletter of credit, the merchant may request payment using another paymentinstrument. Moreover, the merchant may split payment between the limiteduse digital letter of credit and the other payment instrument(s).

In other embodiments, the user's communication device receives thelimited use digital letter of credit from the payment provider. Thewireless beacon may have network capabilities, which may receive thelimited use digital letter of credit and communicate the limited usedigital letter of credit to the user's communication device. In otherembodiments, the payment provider may communicate the limited usedigital letter of credit to the communication device over the network.The payment provider may digitally sign the limited use digital letterof credit using a key of a public/private key pair to authenticate theletter of credit.

Once the communication device receives the limited use digital letter ofcredit, the user may be alerted of the limited use digital letter ofcredit. The communication device may also display the limitations on useof the limited use digital letter of credit to the user. The user maythen shop for items. Once the user is ready to purchase items, the usermay bring the items with their communication device to a checkoutcounter or payment station at the merchant's location. The merchant or amerchant employee may enter the items into a transaction. The merchantmay communicate the transaction to the communication device, where theuser may view the details of the transaction using the communicationdevice. The user and/or the communication device may determine whetherthe transaction meets the limitations on use of the limited use digitalletter of credit or exceeds such limitations. If the transactions meetsthe limitations on use, the communication device may allow for the userto communicate the limited use digital letter of credit to the merchantdevice for processing of the transaction (e.g., for payment for thetransaction). The communication device may transmit the limited usedigital letter of credit to the merchant device using short rangewireless communications, for example, one of near field communication,radio communication, infrared communication, Bluetooth communication,Bluetooth Low Energy (BLE) communication, LTE Direct communication, andWiFi communication. The limited use letter of credit may be communicatedto merchant device by the communication device with a local key toauthenticate the letter of credit.

The merchant may then retrieve payment from the payment provider usingthe limited use digital letter of credit. Since the payment provider hasdigitally signed the letter of credit and verified that the paymentprovider will later honor the amount of credit in the letter of credit,the merchant may asynchronously retrieve payment for the transaction atsome later time. If the user does not use all of the credit in thelimited use digital letter of credit, the merchant device may amend theletter of credit to have a leftover amount of credit after the amountfor the transaction. The merchant device may therefore have thepublic/private key pair to amend the letter of credit. The amendedletter of credit may be communicated back to the user device and may behonored for the leftover amount of credit restricted by any additionallimitations on use of the limited use digital letter of credit.

Again, if the transaction exceeds the limitations on use in the limiteduse digital letter of credit, the merchant may request payment usinganother payment instrument. The user may attempt to request a new letterof credit for the amount in the transaction. In other embodiments, theuser may provide payment using a payment token from the paymentprovider, where the payment token includes a payment instrument (e.g., abank account, payment card, and/or payment account with the paymentprovider). Moreover, the merchant may split payment between the limiteduse digital letter of credit and the other payment instrument(s).

FIG. 1 is a block diagram of a networked system 100 suitable forimplementing the processes described herein, according to an embodiment.As shown, system 100 may comprise or implement a plurality of devices,servers, and/or software components that operate to perform variousmethodologies in accordance with the described embodiments. Exemplarydevice and servers may include device, stand-alone, and enterprise-classservers, operating an OS such as a MICROSOFT® OS, a UNIX® OS, a LINUX®OS, or other suitable device and/or server based OS. It can beappreciated that the devices and/or servers illustrated in FIG. 1 may bedeployed in other ways and that the operations performed and/or theservices provided by such devices and/or servers may be combined orseparated for a given embodiment and may be performed by a greaternumber or fewer number of devices and/or servers. One or more devicesand/or servers may be operated and/or maintained by the same ordifferent entities.

System 100 includes a user 102, a communication device 110, wirelessbeacons 130, a merchant device 140 and a payment provider server 150 incommunication directly using short range wireless communications and/orover a network 170. User 102, such as a consumer. May arrive at amerchant location associated with merchant device 140 in order topurchase an item. Communication device 110 may connect with one or moreof wireless beacons 130, which may provide the connection informationhaving an identifier for user 102 and/or communication device 110 topayment provider server 150. Payment provider server 150 may determine adigital letter of credit with associated limitations on use for user102. The limited use digital letter of credit may be communicated to atleast one of communication device 110 and merchant device 140 for use ina transaction between user 102 and the merchant corresponding tomerchant device 140. The merchant may then later resolve payment usingthe limited use digital letter of credit using merchant device 140 withpayment provider server 150.

Communication device 110, wireless beacons 130, merchant device 140, andpayment provider server 150 may each include one or more processors,memories, and other appropriate components for executing instructionssuch as program code and/or data stored on one or more computer readablemediums to implement the various applications, data, and steps describedherein. For example, such instructions may be stored in one or morecomputer readable media such as memories or data storage devicesinternal and/or external to various components of system 100, and/oraccessible over network 170.

Communication device 110 may be implemented using any appropriatehardware and software configured for wired and/or wireless communicationwith wireless beacons 130, merchant device 140, and/or payment providerserver 150. For example, in one embodiment, communication device 110 maybe implemented as a personal computer (PC), a smart phone, laptop/tabletcomputer, wristwatch with appropriate computer hardware resources,eyeglasses with appropriate computer hardware (e.g. GOOGLE GLASS®),other type of wearable computing device, and/or other types of computingdevices capable of transmitting and/or receiving data, such as an IPAD®from APPLE®. Although a communication device is shown, the communicationdevice may be managed or controlled by any suitable processing device.Although only one communication device is shown, a plurality ofcommunication devices may function similarly.

Communication device 110 of FIG. 1 contains a payment module 120, beaconconnection module 112, other applications 114, a database 116, and acommunication module 118. Payment module 120, beacon connection module112, and other applications 114 may correspond to executable processes,procedures, and/or applications with associated hardware. In otherembodiments, communication device 110 may include additional ordifferent software as required.

Payment module 120 may correspond to one or more processes to executemodules and associated specialized hardware of communication device 110to receive a limited use digital letter of credit from payment providerserver 150, display the information for the limited use digital letterof credit to user 102, and complete a transaction with merchant device130 using the limited use digital letter of credit and/or payment tokenshaving another payment instrument. In this regard, payment module 120may correspond to specialized hardware and/or software utilized toprovide a convenient interface to permit user 102 to select paymentoptions and provide payment for items to merchant device 130. Forexample, payment module 120 may be implemented as a user interface whereuser 102 may view information for a received limited use digital letterof credit. Communication device 110 may connect with one or more ofwireless beacons 130, where connection information for the connectionhaving an identifier for user 102/communication device 110 may beprovided to payment provider server 150 for determination of limited usedigital letter of credit, as discussed herein. Once determined,communication device 110 may receive the limited use digital letter ofcredit from payment provider server 150, for example, through wirelessbeacon 130 and/or over network 170. Payment module 120 may then displayinformation indicating receipt of the limited use digital letter ofcredit as well as the limitations on use of the limited use digitalletter of credit. For example, payment module 120 may display an amountof credit extended to user 102, a validity time period of the letter ofcredit, location validity for the letter of credit, one or moremerchants that the letter of credit is valid for use with, and/or itemsthat may be purchased using the letter of credit.

Payment module 120 may be utilized to receive a transaction frommerchant device 140. Payment module 120 may determine whether thetransaction meets or exceeds the limitations of the limited use digitalletter of credit (i.e., whether the limited use digital letter of creditis valid for payment of the transaction). If the limited use digitalletter of credit is valid for the transaction, payment module 120 maycommunicate the limited use digital letter of credit to merchant device140. Payment module 120 may communicate the limited use digital letterof credit to merchant device 140 using short range wirelesscommunications, for example, one of near field communication, radiocommunication, infrared communication, Bluetooth communication,Bluetooth Low Energy (BLE) communication, LTE Direct communication, andWiFi communication. User 102 may tap, swipe, or otherwise motioncommunication device 110 with merchant device 140 or another nearbycommunication module to communicate the limited use digital letter ofcredit. In other embodiments, payment module 120 may communicate thelimited use digital letter of credit to merchant device 140, which maydetermine whether the transaction meets or exceeds the limitations ofthe limited use digital letter of credit. In such embodiments,communication device 110 may receive the results of the determinationfrom merchant device 140 (including a request for a payment instrumentor token if the limited use digital letter of credit exceeds thelimitations of use).

However, where the transaction exceeds the limitations on use of thelimited use digital letter of credit, payment module 102 may also allowuser 102 to enter payment options for storage by communication device110, provide those payment options on checkout/payment of one or moreitems, request a payment token from payment provider server 150, and/orcomplete a transaction for the item(s) through a purchase request forthe item(s). In some embodiments, payment module 120 may correspond moregenerally to a web browser configured to view information available overthe Internet or access a website corresponding to a payment serviceprovider (e.g., payment provider server 150). Payment module 120 and/orpayment provider server 150 may utilize user financial information, suchas a credit card, bank account, or other financial account, as a paymentinstrument when providing payment information in the form of a paymenttoken to merchant device 130. Additionally, a user account with paymentprovider, such as payment provider server 150, may be utilized as thepayment instrument. In various embodiments, the payment token may becommunicated to merchant device 130 directly or through one or more ofwireless beacons 130. The payment token may also include identificationof the item(s) for purchase and a request to purchase the items. Paymentmodule 120 may also receive a transaction history, such as a receipt,from one or more of merchant device 140 and payment provider server 150.

Beacon connection module 112 may correspond to one or more processes toexecute modules and associated devices of communication device 110 toestablish a connection with one or more of wireless beacons 130established throughout the merchant location. In this regard, beaconconnection module 112 may correspond to specialized hardware and/orsoftware utilized to connect to one or more of wireless beacons 130 inorder to receive short range wireless communications from wirelessbeacons 130 at the merchant location and transmit information towireless beacons 130, including check-in information for a check-inprocess with merchant device 140 (e.g., an identifier for user102/communication device 110). Wireless beacons 130 may be locatedwithin, nearby, or associated with the merchant location and/or asub-location within the merchant location, such as an entrance, aisle,sales area, and/or checkout. Beacon connection module 112 maycommunicate with one or more of wireless beacons 130 to generateconnection information for user 102. The connection information mayidentify user 102 as located at the merchant location and/orsub-location. The connection information may further include anidentifier for user 102 and/or communication device 110, which may becommunicated to payment provider server 150 by wireless beacons 130, asdiscussed herein.

Beacon connection module 112 may execute in the background of anoperating system of communication device 110 and be configured toestablish connections, using communication module 118 of communicationdevice 110, with one or more of wireless beacons 130. The connection maybe established with or without user input from user 102. For example,wireless beacons 130 may broadcast a token, such as a universally uniqueidentifier (UUID), for reception by beacon connection module 112, aswill be explained in more detail herein. Beacon connection module 112may utilize communication module 118 of communication device 110 toreceive the token. If beacon connection module 112 acknowledges the UUIDas identifying wireless beacons 130, merchant device 140, and/or paymentprovider server 150 (e.g., if beacon connection module 112 determinesthe UUID corresponds to a request to complete a check-in), beaconconnection module 112 may transmit an identifier corresponding to user102 and/or communication device 110 back to the one or more of wirelessbeacons 130 transmitting the first identifier. Beacon connection module112 may utilize communication module 118 of communication device 110 tocommunicate with one or more of wireless beacons 130 (e.g., over nearfield communication, Bluetooth, Bluetooth Low Energy, radio, infrared,LTE Direct, or other connection). The identifier from communicationdevice 110 may include, be transmitted with, concatenated with, orotherwise bundled with the identifier received from the one or more ofwireless beacons 130 transmitting the first identifier. In otherembodiments, different information may be transmitted to wirelessbeacons 130, such as a name or other personal information for user 102.Thus, the information transmitted to wireless beacons 130 does not needto be utilized to process and/or complete a check-in with merchantdevice 140 in all embodiments. Once a connection is established withbeacon connection module 112, one or more of wireless beacons 130 maycommunicate information to communicate device 110, such a limited usedigital letter of credit and/or payment token for use by payment module120.

In various embodiments, one or more features of payment module 120and/or beacon connection module 112 may be incorporated in the sameapplication so as to provide their respective features in oneapplication.

Communication device 110 includes other applications 114 as may bedesired in particular embodiments to provide features to communicationdevice 110. For example, other applications 114 may include securityapplications for implementing client-side security features,programmatic client applications for interfacing with appropriateapplication programming interfaces (APIs) over network 170, or othertypes of applications. Other applications 114 may also include email,texting, voice and IM applications that allow a user to send and receiveemails, calls, texts, and other notifications through a network. Invarious embodiments, other applications 114 may include financialapplications, such as banking, online payments, money transfer, or otherapplications associated with payment provider server 170. Otherapplications 114 may include browser, social networking, and/or mappingapplications, which may also be used in conjunction with beaconconnection module 112 and/or payment module 120. Other applications 114may contain software programs, executable by a processor, including agraphical user interface (GUI) configured to provide an interface to theuser.

Communication device 110 may further include database 116 which mayinclude, for example, identifiers such as operating system registryentries, cookies associated with payment module 120, beacon connectionmodule 112, and/or other applications 114, identifiers associated withhardware of communication device 110, or other appropriate identifiers,such as identifiers used for payment/user/device authentication oridentification. Identifiers in database 116 may be used by apayment/credit provider to associate communication device 110 with aparticular account maintained by the payment/credit provider. Database116 may include communication device tokens and/or encryption keys,including an encryption key of wireless beacons 130, and/or paymentprovider server 150. Database 116 may include received information,including a limited use digital letter of credit, a public key of aprivate/public (e.g., asymmetric) key pair used to sign the limited usedigital letter of credit, a payment token, and/or transactioninformation.

Communication device 110 includes at least one communication module 118adapted to communicate with wireless beacons 130, merchant device 140,and/or payment provider server 150. In various embodiments,communication module 118 may include a DSL (e.g., Digital SubscriberLine) modem, a PSTN (Public Switched Telephone Network) modem, anEthernet device, a broadband device, a satellite device and/or variousother types of wired and/or wireless network communication devicesincluding microwave, radio frequency, infrared, Bluetooth, and nearfield communication devices. Communication module 118 may communicatedirectly with wireless beacons 130 using short range communications,such as Bluetooth Low Energy, LTE Direct, radio frequency, infrared,Bluetooth, and near field communications.

Wireless beacons 130 may be maintained, for example, by a merchant formerchant device 140 and/or payment provider server 150. Wireless beacons130 may be implemented using any appropriate hardware and softwareconfigured for wireless communication with communication device 110,merchant device 140, and/or payment provider server 150. For example, inone embodiment, wireless beacons 130 may be implemented as a dongledevice including a hardware processor and a communication module, forexample, connected to device at the location of the merchant. Wirelessbeacons 130 may also be implemented as a device incorporated within apersonal computer (PC), a smart phone, laptop/tablet computer, and/orother types of computing devices capable of transmitting and/orreceiving data. Wireless beacons 130 may also act as a stand-alonedevice including a processor, communication module, and/or networkinterface component configured to communicate with communication device110, merchant device 140, and/or payment provider server 150. Althoughwireless beacons 130 are described as a plurality of wireless beaconsset up at a merchant location for merchant device 140, in variousembodiments, wireless beacons 130 may correspond to a single wirelessbeacon established at the merchant location and/or a sub-location withinthe merchant location.

Wireless beacons 130 may be located at a physical location correspondingto merchant device 140 (e.g., a merchant location, such as a retaillocation, merchant storefront, etc.). Wireless beacons 130 of FIG. 1contains processes, procedures, and/or applications executable by ahardware processor, for example, a software program, configured tointeract with communication device 110, merchant device 140, and/orpayment provider server 150. Thus, regardless of the implementation ofwireless beacons 130, as discussed above, each of wireless beacons 130utilize a connection module 132 and a communication module 134. In otherembodiments, wireless beacons 130 may include additional or differentsoftware and devices as required.

Connection module 132 may correspond to an application for transmittingrequests to establish a connection between a device (e.g., communicationdevice 110) and one of wireless beacons 130. The requests may be uniqueto each of wireless beacons 130 and form a connection with only thematching one of wireless beacons 130. Thus, wireless beacons 130 mayutilize short range wireless communications (e.g., BLE, LTE Direct,WiFi, etc.) of wireless beacons 130 to transmit the requests toestablish a connection, including an identifier such as a UniversallyUnique Identifier (UUID). If communication device 110 receives a requestto establish the connection with wireless beacons 130 and responds withan identifier for user 102/communication device 110 (potentiallyincluding the UUID and other information necessary to effectuate acheck-in for user 102), wireless beacons 130 to ramp up in power andcreate a connection between communication device 110 and one of wirelessbeacons 130.

Each of wireless beacons 130 may uniquely transmit the request toestablish the connection with wireless beacons 130 as a short rangewireless communication (e.g. a BLE protocol communication) including a“wake up” process and/or a token for the one of wireless beacons 130transmitting the request. In other embodiments, the request and/orconnection may utilize near field communication, radio communication,infrared communication, or Bluetooth communication. Additionally,although wireless beacons 130 may utilize BLE protocol communications toeffectuate an “always on” type service where the UUID and “wake up”process are transmitted continuously, other communication protocols usedto provide an “always on” service may include QUALCOMM® LTE Direct orsimilar device-to-device communication technology. BLE and LTE Directmay both be utilized to provide discovery of nearby devices to wirelessbeacons 130 (e.g., communication device 110) and establishment of aconnection for data transfers.

Communication device 110 may only pick up the request based on thesignal range and/or physical context for one of wireless beacons 130transmitting the request within the location. For example, one ofwireless beacons 130 established at a merchant location and may belimited in range only to connect to communication device 110 ifcommunication device 110 is located at the merchant location. Onceconnected, connection information may be generated that may include anidentifier for user 102/communication device 110. After connectionmodule 132 receives an identifier from communication device 110,connection module 132 may communicate the connection information withthe identifier to payment provider server 150 for determination of alimited use digital letter of credit. Additionally, connection module132 may cause wireless beacons 130 to keep a communication channel openbetween communication device 110, merchant device 140, and/or paymentprovider server 150 for passing additional information, such as thelimited use digital letter of credit to merchant device 140 and/orobtaining a payment token from payment provider server 150 whennecessary.

In various embodiments, wireless beacons 130 includes at least onecommunication module 134 adapted to communicate with communicationdevice 110, merchant device 140, and/or payment provider server 150.Communication module 134 may include a DSL (e.g., Digital SubscriberLine) modem, a PSTN (Public Switched Telephone Network) modem, anEthernet device, a broadband device, a satellite device and/or variousother types of wired and/or wireless network communication devicesincluding microwave, radio frequency, infrared, Bluetooth, and nearfield communication devices. Communication module 134 may communicatewith communication device 110 and/or merchant device 140 using shortrange communications, such as radio frequency, infrared, Bluetooth, andnear field communications.

Merchant device 140 may be implemented using any appropriate hardwareand software configured for wired and/or wireless communication withcommunication device 110, wireless beacons 130, and/or payment providerserver 150. For example, merchant device 140 may be implemented as apersonal computer (PC), a smart phone, laptop computer, wristwatch withappropriate computer hardware resources, eyeglasses with appropriatecomputer hardware (e.g. GOOGLE GLASS®) and/or other types of computingdevices capable of transmitting and/or receiving data, such as an IPAD®from APPLE®. Although a merchant device is shown, the merchant devicemay be managed or controlled by any suitable processing device. Althoughonly one merchant device is shown, a plurality of merchant devices mayfunction similarly, for example, in possession of one or more merchantsor merchant employees at a merchant location.

Merchant device 140 of FIG. 1 contains a sales module 142, otherapplications 144, a database 146, and a communication module 148. Salesmodule 142 and other applications 144 may correspond to processes,procedures, and/or applications executable by a hardware processor, forexample, a software program. In other embodiments, merchant device 140may include additional or different software as required.

Sales module 142 may correspond to one or more processes to executemodules and associated devices of merchant device 140 to provide aconvenient interface to permit a merchant for merchant device 140 toenter, view, and/or process items/services user 102 wishes to purchase.In this regard, sales module 142 may correspond to specialized hardwareand/or software utilized by merchant device 140 that may be implementedas an application having a user interface enabling the merchant to enterthe items user 102 has selected for purchase (e.g., through input by themerchant and/or user 102, scanning the items, etc.). Sales module 142may further enable the merchant to view the items for purchase by user102, enter coupons and/or discounts for the items, edit the orderincluding adding, removing, and/or modifying items, or other functionswith regards the selected items/services. Once the items have beenarranged into an order for purchase by user 102, a total may becalculated and a transaction may be engaged with user 102 to completepayment for the selected items. Sales module 142 may request paymentcovering the selected items from user 102. Thus, sales module 142 mayreceive a payment instrument from user 102 to complete a transaction forthe selected items. The payment instrument may correspond to cash,payment cards, checks, and/or payment accounts with payment providerserver 170, in various embodiments. The payment instrument may alsocorrespond to a limited use digital letter of credit, as discussedherein. Sales module 142 may later (e.g., asynchronously) resolvepayment for the transaction using the limited use digital letter ofcredit with payment provider server 150. Where the limitations of use ofthe limited use digital letter of credit are exceeded by thetransaction, the payment instrument may instead correspond to a paymenttoken generated by payment provider server 150. Once a transaction isprocessed and/or completed by sales module 142 for the selected items byuser 102, a transaction history (e.g., receipt) may be generated andprovided to one or more of user 102, communication device 110, and/orpayment provider server 150.

Merchant device 140 includes other applications 144 as may be desired inparticular embodiments to provide features to merchant device 140. Forexample, other applications 144 may include security applications forimplementing client-side security features, programmatic clientapplications for interfacing with appropriate application programminginterfaces (APIs) over network 170, or other types of applications. Invarious embodiments, other applications 144 may include financialapplications, such as banking, online payments, money transfer, or otherapplications associated with payment provider server 170. Otherapplications 144 may contain other software programs, executable by aprocessor, including a graphical user interface (GUI) configured toprovide an interface to the user.

Merchant device 140 may further include database 146 which may include,for example, identifiers such as operating system registry entries,cookies associated with item tag monitoring module 160, sales module142, and/or other applications 144, identifiers associated with hardwareof merchant device 140, or other appropriate identifiers, such asidentifiers used for payment/user/device authentication oridentification. Database 146 may also store user 102's information,including check-in information, an identifier, etc., for user 102.Database 146 may include payment instruments, past transactionhistories, expected checkout times, and/or other past information foruser 102. Database 146 may also store received information, such as alimited use digital letter of credit and/or a payment token.

Merchant device 140 includes at least one communication module 148adapted to communicate with communication device 110, wireless beacons130, and/or payment provider server 150. In various embodiments,communication module 148 may include a DSL (e.g., Digital SubscriberLine) modem, a PSTN (Public Switched Telephone Network) modem, anEthernet device, a broadband device, a satellite device and/or variousother types of wired and/or wireless network communication devicesincluding microwave, radio frequency, infrared, Bluetooth, and nearfield communication devices. Communication module 148 may communicatedirectly with communication device 110 and/or wireless beacons 130 usingshort range communications, such as Bluetooth Low Energy, LTE Direct,radio frequency, infrared, Bluetooth, and near field communications.

Payment provider server 150 may be maintained, for example, by an onlinepayment service provider, which may provide payment services and/orprocessing for financial transactions on behalf of users, includingprocessing of received payment tokens for a transaction. In this regard,payment provider server 150 includes one or more processing applicationswhich may be configured to interact with communication device 110,wireless beacons, and/or merchant device 140 to facilitate payment for atransaction. In one example, payment provider server 150 may be providedby PAYPAL®, Inc. of San Jose, Calif., USA. However, in otherembodiments, payment provider server 150 may be maintained by or includea credit provider, financial services provider, financial data provider,and/or other service provider, which may provide payment services touser 102 and/or the merchant associated with merchant device 130.

Payment provider server 150 of FIG. 1 includes credit authorizationmodule 160, a transaction processing module 152, other applications 154,a database 156, and a network interface component 158. Creditauthorization module 160, transaction processing module 152, and otherapplications 154 may correspond to executable processes, procedures,and/or applications with associated hardware. In other embodiments,payment provider server 150 may include additional or different moduleshaving specialized hardware and/or software as required.

Credit authorization module 160 may correspond to one or more processesto execute modules and associated specialized hardware of paymentprovider server 150 to access connection information generated by aconnection between communication device 110 and one or more of wirelessbeacons 130, determine credit eligibility and/or worthiness of user 102using an identifier in the connection information, determine a limiteduse digital letter of credit using the credit eligibility, andcommunicate the limited use digital letter of credit to communicationdevice 110, wireless beacons 130 and/or merchant device 140. In thisregard, transaction processing module 152 may correspond to specializedhardware and/or software to access the connection information, forexample, from database 156. The connection information may include anidentifier for user 102 and/or communication device 110. Using theidentifier, information for the user may be determined. For example, theidentifier may be used to access user information, such as a name,address, or other identification information. The user information mayfurther include at least one financial indicator of credit worthiness ofuser 102, such as a credit rating, available collateral, availablefunds, past transaction histories, debts of user 102, and assets of user102. The financial indicator(s) may be used to determine an amount ofcredit to extend to user 102. Thus, once the user information for user102 is accessed using the identifier, credit authorization module 160may determine whether to extend credit to user 102 and how much creditto extend to user 102.

Based on the amount of credit to extend to user 102, a digital letter ofcredit for user 102 may be determined. The digital letter of credit mayalso include limitations on use so that the digital letter of credit mayonly be utilized in conformity with one or more terms limiting the useof the digital letter of credit. Limitations on use of the digitalletter of credit may include time limitations, location limitations,merchant with which the digital letter of credit may be utilized, and/oritems that the digital letter of credit may be used to purchase. Oncethe limitations on use are determined, a limited use digital of creditmay be determined having the amount of credit and the limitations onuse. The limited use digital letter of credit may be communicated towireless beacons 130 for communication to communication device 110. Inother embodiments, the limited use digital letter of credit may becommunicated directly to communication device 110 and/or merchant device140. Credit authorization module 160 may further digitally sign thelimited use digital letter of credit using an asymmetric key pair andprovide a public key to communication device 110 and/or merchant device140 to authenticate the limited use digital letter of credit. User 102may then utilize the limited use digital letter of credit to providepayment to merchant device 140, as discussed herein. Thus, when themerchant associated with merchant device 140 wishes to resolve thepayment with payment provider server 150, the merchant (e.g., throughmerchant device 140) may provide the limited use digital letter ofcredit to payment provider server 150 with terms of the transaction(e.g., a payment amount), which may provide payment through transactionprocessing module 152. Where the transaction does not meet the terms ofthe limited use digital letter of credit, user 102 may request a paymenttoken from transaction processing module 152 as well.

Transaction processing module 152 may correspond to one or moreprocesses to execute modules and associated specialized hardware ofpayment provider server 150 to receive and/or transmit information fromcommunication device 110 and/or merchant device 140 for processing andcompletion of one or more transactions initiated by user 102. In thisregard, transaction processing module 152 may correspond to specializedhardware and/or software to process a received transaction fromcommunication device 110 and/or merchant device 140 by receiving thetransaction from communication device 110 and/or merchant device 140with a payment request for a payment for the transaction. The paymentrequest may identify a limited use digital letter of credit or a paymenttoken, including a payment instrument and identification of thetransaction, and may be encrypted prior to transmission to transactionprocessing module 152 to prevent unauthorized receipt of a paymentinstrument. Where the payment request identifies a limited use digitalletter of credit, transaction processing module 152 may provide paymentto the merchant associated with merchant device 140 (e.g., to a merchantaccount for the merchant). Transaction processing module 152 may thenrequire payment from user 102, such as from a payment instrument storedto payment provider server 150 and/or a bill sent to user 102 forpayment.

Where user 102 requires a payment token from transaction processingmodule 152, the payment token may include information corresponding touser identifiers, user financial information/identifiers, transactioninformation and/or other identifiers. Additionally, the payment tokenmay include a payment amount and terms of payment for the transaction.Once received, transaction processing module 152 may utilize a paymentaccount or financial information (e.g., a payment instrument such as acredit/debit card, bank account, etc.) of user 102 to render payment forthe transaction. Transaction processing module 152 may receive purchaseauthorizations, in certain embodiments, and process payments fortransaction in accordance with the purchase authorizations. Payment maybe made to merchant device 140 using the payment instrument and theterms of the payment request. Additionally, transaction processingmodule 152 may provide transaction histories, including receipts, tocommunication device 110, merchant device 130, and/or merchant server140 for completion and documentation of the financial transaction. Suchtransaction histories may be utilized to determine additional itemsrequired with future purchases by user 102 and/or other users.

In various embodiments, payment provider server 150 includes otherapplications 154 as may be desired in particular embodiments to providefeatures to payment provider server 150. For example, other applications154 may include security applications for implementing client-sidesecurity features, programmatic client applications for interfacing withappropriate application programming interfaces (APIs) over network 170,or other types of applications. Other applications 154 may containsoftware programs, executable by a processor, including a graphical userinterface (GUI), configured to provide an interface to user 102 whenaccessing payment provider server 150. In various embodiments where notprovided by credit authorization module 160 and/or transactionprocessing module 152, other applications 154 may include connectionand/or communication applications, which may be utilized tocommunication information to communication device 110 and/or merchantdevice 130.

Additionally, payment provider server 150 includes database 156. Aspreviously discussed, user 102 and/or the merchant corresponding tomerchant device 140 may establish one or more payment accounts withpayment provider server 150. Payment accounts in database 156 mayinclude user/merchant information, such as name, address, birthdate,payment/funding information, additional user financial information,and/or other desired user data. User 102 and/or the merchant may link totheir respective payment accounts through a user, merchant, and/ordevice identifier. Thus, when an identifier is transmitted to paymentprovider server 150, e.g. from communication device 110 and/or merchantdevice 140, a payment account belonging to user 102 and/or the merchantmay be found. Payment amounts may be deducted from one payment accountand paid to another payment account. In other embodiments, user 102and/or the merchant may not have previously established a paymentaccount and may provide other financial information to payment providerserver 150 to complete financial transactions, as previously discussed.Database 156 may further include information used by creditauthorization module 160, such as user information used to determine anamount of credit to extend to user 102 and/or user/merchant/locationinformation used to determine limitation on use of a digital letter ofcredit.

In various embodiments, payment provider server 150 includes at leastone network interface component 158 adapted to communicate communicationdevice 110, wireless beacons 130, and/or merchant device 140 overnetwork 170. In various embodiments, network interface component 158 maycomprise a DSL (e.g., Digital Subscriber Line) modem, a PSTN (PublicSwitched Telephone Network) modem, an Ethernet device, a broadbanddevice, a satellite device and/or various other types of wired and/orwireless network communication devices including microwave, radiofrequency (RF), and infrared (IR) communication devices.

Network 170 may be implemented as a single network or a combination ofmultiple networks. For example, in various embodiments, network 170 mayinclude the Internet or one or more intranets, landline networks,wireless networks, and/or other appropriate types of networks. Thus,network 170 may correspond to small scale communication networks, suchas a private or local area network, or a larger scale network, such as awide area network or the Internet, accessible by the various componentsof system 100.

FIG. 2 is an exemplary merchant environment with users receiving limiteduse digital letters of credit on arrival or checkin at a merchantlocation for use in transactions with a merchant at the merchantlocation, according to an embodiment. Environment 200 of FIG. 2 includesa user 102 a utilizing a communication device 110 a, a user 102 butilizing a communication device 110 b, and a user 102 c utilizing acommunication device 110 c, all corresponding generally to user 102utilizing communication device 110, respectively, of FIG. 1. Environment200 further includes a wireless beacon 130 a corresponding generally toone or more of wireless beacons 130 of FIG. 1.

Environment 200 includes a merchant location 280 where users 102 a-c mayvisit in order to purchase items 284, such as televisions, computers,and other electronics. Wireless beacon 130 a may be established at anentrance 282 so that when users 102 a-c pass through entrance 282 toshop at merchant location 280, communication devices 110 a-c may pairwith wireless beacon 130 a and generate connection information having anidentifier for user 102 a-c, respectively. For example, when arriving atmerchant location 280, user 102 a in possession of communication device110 a may have communication device 110 a connect with wireless beacon130 a. The connection may establish connection information identifyinguser 102 a as located at merchant location. The connection informationmay be communicated to a payment provider server, which may thendetermine a limited use digital letter of credit for user 102 a.Similarly, limited use digital letters of credit may also be determinedfor users 102 b and 102 c when arriving at merchant location 280.

While shopping at merchant location 280, user 102 b may view one or moreof items 284 that user 102 b may wish to purchase. User 102 b may havepreviously received a limited use digital letter of credit on arrival atmerchant location 280 through communication device 110 b. However, thelimited use digital letter of credit for user 102 b may have expiredwhile shopping items 284 or a selected item from items 284 may not meetlimitations on use of the limited use digital letter of credit. Thus,user 102 b may require an updated or new limited use digital letter ofcredit, or user 102 b may request a payment token to complete paymentfor the selected item using communication device 110 b. For example,communication device 110 b may pair with wireless beacon 130 a again andrequest another limited use digital letter of credit if the previousletter of credit has expired. However, if the limitations of use of adigital letter of credit provided to user 102 b are exceeded by theitem, user 102 b may be required to provide payment using anotherpayment instrument and/or payment token from the payment provider (i.e.,not using credit extended to user 102 b).

User 102 c is shown at a checkout 286 where user 102 c may completepayment for an item by providing payment to merchant 204. User 102 c mayhave a valid limited use digital letter of credit, which may coverpayment for an item user 102 c wishes to purchase at checkout 286. Thus,user 102 c may provide the limited use digital letter of credit tomerchant 204. User 102 c may communicate the limited use digital letterof credit to merchant device 140 using communication device 110 c. Suchcommunications may utilize short range wireless communications betweencommunication device 110 c and merchant device 140. The limited usedigital letter of credit may also be communicated to merchant device 140with a local key allowing for authentication of the letter of credit.Merchant 204 may then complete the transaction with user 102 c using theletter of credit, and may later resolve payment for the transaction witha payment provider issuing the letter of credit. Merchant 204 mayasynchronously resolve the payment with the payment provider so that thetransaction is quickly completed with user 102 c without the need forcommunication with the payment provider by merchant device 140. Thepayment provider may honor the payment amount in the letter of credit,and may retrieve payment from user 102 c, such as through a paymentaccount or payment instrument held by the payment provider or issuing abill to user 102 c.

FIG. 3 is an exemplary system environment showing a user's communicationdevice receiving a limited use digital letter of credit from a paymentprovider based on the user's credit worthiness and utilizing the limiteduse digital letter of credit for a transaction with a merchant device,according to an embodiment. Environment 300 includes communicationdevice 110, merchant device 140, and payment provider server 150 ofFIG. 1. The below described hardware and/or software modules executefunctions as described herein with respect to environment 100.

Communication device 110 executes payment module 120 having specializedhardware and/or software modules and processes described herein inreference to FIG. 1. In this regard, payment module 120 displays one ormore limited use digital letters of credit provided to a user (notshown) of communication device 110 after determination of the limiteduse digital letter(s) of credit by payment provider server 150.Communication device 110 may first connect with a wireless beacon onarrival at a merchant location to generate connection information havingan identifier for the user/communication device 110. The connectioninformation may be communicated to payment provider server 150, whichexecutes credit authorization module 160 having specialized hardwareand/or software modules and processes described herein in reference toFIG. 1. Thus, credit authorization module 160 includes an identifier1100 from the connection information. Identifier 1100 may be utilized todetermine credit worthiness 1102, such as information for a creditrating 1104, past transactions 1106, and payment account 1108. Usingcredit worthiness 1102, credit authorization module 160 may determine aletter of credit 1000, which may be communicated to communication device110.

Payment module 120 includes letter of credit 1000, which may include anamount of credit and limitations on use of letter of credit 1000. Thus,letter of credit 1000 includes amount 1002 of extended credit to theuser, and use limitation 1004 having limitations on use with a merchant1006, a location 1008, a time 1010, and purchases 1012. Payment module120 may further include information for connected device 1014, which maydisplay devices and/or beacons that communication device 110 isconnected with for use in obtaining letter of credit 1000 and/orcompleting a transaction. Connected devices 1014 include beacons 1016(e.g., a wireless beacon) and devices 1018 (e.g., merchant device 140).Payment module 120 may receive transaction information, which may beprocessed by payment module 120 to determine if letter of credit 1000may be utilized for a transaction 1020. Transaction 1020 includes items1022, a total 1024, and a selected option for a payment method 1026,such as letter of credit 1000 and/or payment account 1028. In otherembodiments, merchant device 140 may determine whether letter of credit1000 may be utilized for transaction 1020.

Merchant device 140 executes a sales module 142 having specializedhardware and/or software modules and processes described herein inreference to FIG. 1. Sales module 142 may be utilized to completetransaction 1020 with communication device 110, for example, usingletter of credit 1000. In this regard, sales module 142 includestransaction 1020 having items 1022 and a total 1024. In order tocomplete transaction 1020, sales module 142 may require a paymentinstrument to be provided by the user of communication device 110. Thus,sales module 142 further includes a selected payment method 1200 havingletter of credit 1000 communicated by communication device 110 tomerchant device 140. Sales module 142 may further process letter ofcredit 1000 to generate a processed 1202 status for completion oftransaction 1020.

FIG. 4 is a flowchart of an exemplary process for wireless beaconconnections for providing digital letters of credit on detection of auser at a location, according to an embodiment. Note that one or moresteps, processes, and methods described herein may be omitted, performedin a different sequence, or combined as desired or appropriate.

At step 402, connection information comprising an identifier for a userlocated at a merchant location is received, by a network interfacecomponent, wherein the first connection information is generated by afirst connection between a communication device of the user and awireless beacon established at the merchant location using short rangewireless communications. The connection information may then be accessedby a credit authorization module comprising at least one hardwareprocessor. User information comprising at least one financial indicatorof credit worthiness for the user is accessed, by the creditauthorization module, using the identifier, at step 404. An amount ofcredit to extend to the user without utilizing a payment account of theuser is determined, using the at least one financial indicator of creditworthiness, by the credit authorization module, at step 406.

At step 408, a limited use digital letter of credit for the user isgenerated, by the credit authorization module, using the amount ofcredit. The limited use digital letter of credit may be limited in useby an amount of time the limited use digital letter of credit is validfor, a location for where the limited use digital letter of credit isvalid, a merchant with which the limited use digital letter of credit isvalid, and a type of purchase with which the limited use digital letterof credit is valid. The communication device may communicate the limiteduse digital letter of credit to a merchant device to process a paymentfor a transaction between the user and a merchant associated with themerchant device. The communication device may communicate the limiteduse digital letter of credit to the merchant device using short rangewireless communications comprising one of near field communication,radio communication, infrared communication, Bluetooth communication,Bluetooth Low Energy (BLE) communication, LTE Direct communication, andWiFi communication. Thus, the merchant device may receive the paymentfor the transaction from a payment provider using the limited usedigital letter of credit, which may occur asynchronously from completingthe transaction with the user. A transaction processing module mayprovide the payment to the merchant and resolve an amount for thepayment with the user using at least one of a banking account of theuser, a payment card of the user, and a payment account of the user withthe payment provider.

The merchant device may determine whether the transaction exceedslimitations (including not meeting conditions) on use of the limited usedigital letter of credit. For example, the merchant device may processthe transaction using the limited use digital letter of credit if thetransaction does not exceed the limitations on use of the limited usedigital letter of credit. However, the merchant device may request adifferent payment instrument if the transaction exceeds the limitationson use of the limited use digital letter of credit. The differentpayment instrument may comprise at least one of a banking account of theuser, a payment card of the user, and a payment account of the user withthe payment provider. In such embodiments, the transaction processingmodule may receive a request for a payment token from the communicationdevice of the user and generates the payment token using at least one ofthe banking account, the payment card, and the payment account, whereinthe merchant device receives a payment for the transaction using thepayment token. In other embodiments, the communication device mayreceive a transaction between the user and a merchant from a merchantdevice for the merchant, wherein the communication device determineswhether the transaction exceeds limitations on use of the limited usedigital letter of credit. The communication device may also request oneof a new letter of credit and a payment token if the transaction exceedsthe limitations on use of the limited use digital letter of credit.

The limited use digital letter of credit may be renewed if the limiteduse digital letter of credit expires. For example, the creditauthorization module may determine that the limited use digital letterof credit has expired based on limitation of use of the limited usedigital letter of credit. The credit authorization module may thendetermine that the user is located at the merchant location in order torenew the limited use digital letter of credit. The credit authorizationmodule may determine that the user is located at the merchant locationby receiving second communication information comprising a secondconnection between the communication device of the user and the wirelessbeacon established at the merchant location using the short rangewireless communications. After processing of a transaction using thelimited use digital letter of credit, one of the communication deviceand a merchant device at the merchant location may amend the limited usedigital letter of credit after processing a payment to a merchant at themerchant location to generate a new letter of credit having a leftoveramount after the payment to the merchant.

FIG. 5 is a block diagram of a computer system suitable for implementingone or more components in FIG. 1, according to an embodiment. In variousembodiments, the communication device may comprise a personal computingdevice (e.g., smart phone, a computing tablet, a personal computer,laptop, a wearable computing device such as glasses or a watch,Bluetooth device, key FOB, badge, etc.) capable of communicating withthe network. The service provider may utilize a network computing device(e.g., a network server) capable of communicating with the network. Itshould be appreciated that each of the devices utilized by users andservice providers may be implemented as computer system 500 in a manneras follows.

Computer system 500 includes a bus 502 or other communication mechanismfor communicating information data, signals, and information betweenvarious components of computer system 500. Components include aninput/output (I/O) component 504 that processes a user action, such asselecting keys from a keypad/keyboard, selecting one or more buttons,image, or links, and/or moving one or more images, etc., and sends acorresponding signal to bus 502. I/O component 504 may also include anoutput component, such as a display 511 and a cursor control 513 (suchas a keyboard, keypad, mouse, etc.). An optional audio input/outputcomponent 505 may also be included to allow a user to use voice forinputting information by converting audio signals. Audio I/O component505 may allow the user to hear audio. A transceiver or network interface506 transmits and receives signals between computer system 500 and otherdevices, such as another communication device, service device, or aservice provider server via network 170. In one embodiment, thetransmission is wireless, although other transmission mediums andmethods may also be suitable. One or more processors 512, which can be amicro-controller, digital signal processor (DSP), or other processingcomponent, processes these various signals, such as for display oncomputer system 500 or transmission to other devices via a communicationlink 518. Processor(s) 512 may also control transmission of information,such as cookies or IP addresses, to other devices.

Components of computer system 500 also include a system memory component514 (e.g., RAM), a static storage component 516 (e.g., ROM), and/or adisk drive 517. Computer system 500 performs specific operations byprocessor(s) 512 and other components by executing one or more sequencesof instructions contained in system memory component 514. Logic may beencoded in a computer readable medium, which may refer to any mediumthat participates in providing instructions to processor(s) 512 forexecution. Such a medium may take many forms, including but not limitedto, non-volatile media, volatile media, and transmission media. Invarious embodiments, non-volatile media includes optical or magneticdisks, volatile media includes dynamic memory, such as system memorycomponent 514, and transmission media includes coaxial cables, copperwire, and fiber optics, including wires that comprise bus 502. In oneembodiment, the logic is encoded in non-transitory computer readablemedium. In one example, transmission media may take the form of acousticor light waves, such as those generated during radio wave, optical, andinfrared data communications.

Some common forms of computer readable media includes, for example,floppy disk, flexible disk, hard disk, magnetic tape, any other magneticmedium, CD-ROM, any other optical medium, punch cards, paper tape, anyother physical medium with patterns of holes, RAM, PROM, EEPROM,FLASH-EEPROM, any other memory chip or cartridge, or any other mediumfrom which a computer is adapted to read.

In various embodiments of the present disclosure, execution ofinstruction sequences to practice the present disclosure may beperformed by computer system 500. In various other embodiments of thepresent disclosure, a plurality of computer systems 500 coupled bycommunication link 518 to the network (e.g., such as a LAN, WLAN, PTSN,and/or various other wired or wireless networks, includingtelecommunications, mobile, and cellular phone networks) may performinstruction sequences to practice the present disclosure in coordinationwith one another.

Where applicable, various embodiments provided by the present disclosuremay be implemented using hardware, software, or combinations of hardwareand software. Also, where applicable, the various hardware componentsand/or software components set forth herein may be combined intocomposite components comprising software, hardware, and/or both withoutdeparting from the spirit of the present disclosure. Where applicable,the various hardware components and/or software components set forthherein may be separated into sub-components comprising software,hardware, or both without departing from the scope of the presentdisclosure. In addition, where applicable, it is contemplated thatsoftware components may be implemented as hardware components andvice-versa.

Software, in accordance with the present disclosure, such as programcode and/or data, may be stored on one or more computer readablemediums. It is also contemplated that software identified herein may beimplemented using one or more general purpose or specific purposecomputers and/or computer systems, networked and/or otherwise. Whereapplicable, the ordering of various steps described herein may bechanged, combined into composite steps, and/or separated into sub-stepsto provide features described herein.

The foregoing disclosure is not intended to limit the present disclosureto the precise forms or particular fields of use disclosed. As such, itis contemplated that various alternate embodiments and/or modificationsto the present disclosure, whether explicitly described or impliedherein, are possible in light of the disclosure. Having thus describedembodiments of the present disclosure, persons of ordinary skill in theart will recognize that changes may be made in form and detail withoutdeparting from the scope of the present disclosure. Thus, the presentdisclosure is limited only by the claims.

What is claimed is:
 1. A device comprising: a non-transitory memorystoring instructions; a processor configured to execute the instructionsto cause the device to: execute, on a display of the device, a userinterface for a payment application; detect, over a network connection,a merchant device at a merchant location in proximity to the device;transmit, over the network connection, connection information comprisinga user identifier to the merchant device; receive, over the networkconnection, a notification presenting on the user interface of thepayment application, a digital letter of credit for a merchantcorresponding to the merchant location of the merchant device, thedigital letter of credit received in response to a determination of anamount of credit to extend to a user associated with the device, theamount of credit determined based on a financial indicator of creditworthiness determined from the user identifier.
 2. The device of claim1, wherein the digital letter of credit is automatically determined by apayment provider associated with the payment application.
 3. The deviceof claim 1, wherein the digital letter of credit is modified by themerchant device.
 4. The device of claim 1, executing the instructionsfurther causes the device to: transmit, over the network connect, arequest for a credit increase on the digital letter of credit.
 5. Thedevice of claim 1, wherein the digital letter of credit is a limitedused digital letter of credit.
 6. The device of claim 5, wherein digitalletter of credit is limited in one of time, merchant location, andamount.
 7. The device of claim 2, wherein the device communicates thedigital letter of credit to the merchant device to process payment for atransaction between the user and the merchant.
 8. The device of claim 7,wherein the merchant device receives the payment for the transactionfrom the payment provider using the digital letter of credit.
 9. Amethod comprising: executing, on a display of a device, a user interfacefor a payment application; detecting, over a network connection, amerchant device at a merchant location in proximity to the device;transmitting, over the network connection, connection informationcomprising a user identifier to the merchant device; receiving, over thenetwork connection, a notification presenting on the user interface ofthe payment application, a digital letter of credit for a merchantcorresponding to the merchant location of the merchant device, thedigital letter of credit received in response to a determination of anamount of credit to extend to a user associated with the device, theamount of credit determined based on a financial indicator of creditworthiness determined from the user identifier.
 10. The method of claim9, wherein the digital letter of credit is automatically determined by apayment provider associated with the payment application.
 11. The methodof claim 9, wherein the digital letter of credit modified by themerchant device.
 12. The method of claim 9, further comprising:transmitting, over the network connect, a request for a credit increaseon the digital letter of credit.
 13. The method of claim 9, wherein thedigital letter of credit is a limited used digital letter of credit. 14.The method of claim 10, wherein the device communicates the digitalletter of credit to the merchant device to process payment for atransaction between the user and the merchant.
 15. The method of claim14, wherein the merchant device receives the payment for the transactionfrom the payment provider using the digital letter of credit.
 16. Anon-transitory machine-readable medium having instructions storedthereon, the instructions executable to cause performance of operationscomprising: executing, on a display of a device, a user interface for apayment application; detect, over a network connection, a merchantdevice at a merchant location in proximity to the device; transmitting,over the network connection, connection information comprising a useridentifier to the merchant device; receiving, over the networkconnection, a notification presenting on the user interface of thepayment application, a digital letter of credit for a merchantcorresponding to the merchant location of the merchant device, thedigital letter of credit received in response to a determination of anamount of credit to extend to a user associated with the device, theamount of credit determined based on a financial indicator of creditworthiness determined from the user identifier.
 17. The non-transitorymachine-readable medium of claim 16, wherein the digital letter ofcredit is automatically determined by a payment provider associated withthe payment application.
 18. The non-transitory machine-readable mediumof claim 16, further comprising: transmitting, over the network connect,a request for a credit increase on the digital letter of credit.
 19. Thenon-transitory machine-readable medium of claim 16, wherein the digitalletter of credit is a limited used digital letter of credit.
 20. Thenon-transitory machine-readable medium of claim 16, wherein the devicecommunicates the digital letter of credit to the merchant device toprocess payment for a transaction between the user and the merchant.